home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Shareware Overload Trio 2
/
Shareware Overload Trio Volume 2 (Chestnut CD-ROM).ISO
/
dir24
/
nosinst.zip
/
PORTINFO.INF
< prev
next >
Wrap
Text File
|
1994-04-25
|
4KB
|
111 lines
USING THE SERIAL PORT TABLE EDITOR
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Press <F10> to select serial port edit mode.
Use the right and left cursor keys or TAB to first
move the cursor to the bottom of the required port
setup column. Press <SPACE> to select that port.
You may now move the cursor up into the port details
to edit them if your port has a non-standard setup.
N.B. "Use" and "Type" fields are TOGGLED by pressing
any key (except <ENTER>, <TAB>, or cursor keys)
Other fields can be edited as soon as the cursor is
under the first character in that field.
Press <ENTER> or <ESC> to finish editing.
!
SERIAL INTERFACE PORTS
~~~~~~~~~~~~~~~~~~~~~~
For NOS to be able to communicate with the outside
world, it requires an interface and a name for that
interface to be specified.
For instance, let's presume for a moment that you are
going to be using a tnc modem connected to serial port
1. In the main startup file, there will be a line
that specifies that you want to send tcp/ip traffic
down serial port 1. But instead of saying "serial
port 1" every time we want to refer to this
input/output port, we give it an alias which
simplifies the whole procedure. This name can be
anything as long as it isn't too long or too strange.
There's little point in getting the computer to work
hard processing long names like "my_tnc_interface" so
to encourage a sane approach, I have set a maximum
limit of 5 characters.
Typical port names are; tnc0, sl0, vhf, uhf, 70cm, 2m,
etc... I'm sure you get the idea.
These names are also referred to in routing tables. A
routing table is the means by which NOS determines
where to send traffic.
!
SLIP LINKS
~~~~~~~~~~
If this is a second station in your setup, you may
wish to connect this station to the primary one using
what is called a SLIP link (Serial Link Interface
Protocol) i.e. a serial wire that connects the other
tcp/ip computer to this one.
At the moment, this installation program only caters
for two types of connection. A serial link to a tnc
(the tnc being used in KISS mode - see your tnc manual
for how to do that), and the SLIP link to another
computer.
By the way, the interface type is "ax25" if it's
driving a tnc.
!
USING DIFFERENT INTERFACES
~~~~~~~~~~~~~~~~~~~~~~~~~~
The installation program will assume that you always
mean serial ports throughout, so when the installation
is complete, you will have to edit the AUTOEXEC.NOS
file so that ATTACH lines refer to your interface
instead. Don't forget to keep the interface name the
same, i.e. if you call a port "vhf", you will need to
retain this name otherwise routing tables etc will not
be correct.
!
WHICH PORT(S) TO USE
~~~~~~~~~~~~~~~~~~~~
You can only specify one port per installation. If you
ask for a port that isn't standard or doesn't exist,
you will see a warning message explaining what has
happened.
!
BASIC RULES
~~~~~~~~~~~
Don't set the baud rate too high as PC's in general
aren't too clever when it comes to serial ports. 4800
baud is plenty fast enough. In fact, if your machine
is an XT or a slow AT, don't set the baud rate to more
than 4800. The baud rate of the computer to tnc link
should never be slower than the radio link speed but
can be set equal to it without causing problems. You
may edit the AUTOEXEC.NOS file ATTACH lines if you
need to change to higher speeds later.
*CAUTION* Your tnc may be set for a computer link
speed of 1200 baud (!) and be in ax25 command mode.
Link Tiny-2's for 4800 baud then use a terminal
program to tell the tnc to go into KISS mode before
running NOS. Usually the commands; KISS ON <enter>
followed by; RESTART <enter> will achieve this if
it's a Tiny-2 or clone.
When connecting your rig and tnc, open the squelch
right up and turn the volume up until you see the DCD
light on constantly. Then, turn the squelch up until
the DCD light just goes out and stays off when there
are no signals coming in. This is a fairly good rule
of thumb approach. Ask SEVERAL of your surrounding
users how they have theirs set up (don't rely on just
one other station as some still have bad setups after
some 5 years plus of operation!).